Skip to content

Conversation

@yusufkandemir
Copy link
Member

What kind of change does this PR introduce?

  • Performance

Does this PR introduce a breaking change?

  • No

The PR fulfills these requirements:

  • It's submitted to the dev branch (or v[X] branch)

Other information:
This is similar to #17756, but for the Vue transform.

I noticed there is still a problem regarding this while working on #17934.

Aside from this use case, it may help with performance with projects that do not have any .vue files and only use .js/.ts files.

which also eliminates the need for ui package to be built in the monorepo before running quasar prepare
yusufkandemir added a commit to yusufkandemir/quasar that referenced this pull request Mar 26, 2025
which runs quasar prepare, which requires ui package to be built due to logic in vite-plugin
removing at least until quasarframework#17935 gets merged
@rstoenescu rstoenescu merged commit ed0bf69 into quasarframework:dev Apr 29, 2025
rstoenescu pushed a commit that referenced this pull request Apr 29, 2025
* chore: migrate to eslint v9

* chore: make more changes for eslint v9 migration

* chore: enable cache for eslint

* chore(vite-plugin): consolidate eslint config

* chore: adjust jsconfig files

* chore(docs): remove outdated stylintrc file
which was for Stylus

* chore: include all projects in VS Code ESLint extension
and simplify it by using mode: auto

* chore: exclude dist directories from VS Code search

* chore: remove failing postinstall script
which runs quasar prepare, which requires ui package to be built due to logic in vite-plugin
removing at least until #17935 gets merged

* chore: rename prepare to prepare:types to avoid unintentional runs
forgot prepare was a special script
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants